Hello, We're running Exchange 2010 with 2 MBX servers and 2 CAS/HUB servers. We are making changes to our domain controllers. In total we have 4 DC's and 2 sites. Server A - Global catalog Site 1 Server B - DC Server C - DC Server D - Global Catalog Site 2 If i'm correct it's best practise to have 1 global catalog per site. Plz correct me if i'm wrong. Currently the servers being used by Echange are Server A and B for CurrentDomainControllers and server B for CurrentConfigDomainControllers. This is shown by running Get-ExchangeServer -status | fl Name, *Domain* Server B needs to be decomissioned, Server A needs to be freed of Exchange requests. Problem is the result of event ID 2080, the AD topology that Exchange pulls from our domain. It only reports Server A and Server B as usable. I've tried looking for more info on event ID 2080, more specific explenation on the different columns and how to configure, as of now I haven't had much success. Output of event ID 2080 : In-site: Server A CDG 1 7 7 1 0 1 1 7 1 Server B CD- 1 6 6 0 0 1 1 6 1 Server C CD- 1 0 0 0 0 0 0 0 0 Out-of-site: Server D CDG 1 7 7 1 0 1 1 7 1 This is why i'm relectant to make changes either with shell or the EMC because i presume Exchange won't accept Server C as a usable Domain Controller. So if you would be so kind plz provide information on: - How to make Exchange report all DC's as usable - If i'm correct in stating Exchange does not need a Global Catalog as originatingserver or config server - How to correctly change the list of DC's Exchange is using (EMC only provides changing configuration domain controller?) Thanx in advance for any assistance. It is greatly appreciated. Regards, Jelle

In terms of your Global Catalog configuration you have two options: 1) Make all your servers Global Catalogs 1) Keep your current configuration but move the Infrastructure Master FSMO role to a server that is NOT a global catalog Both methods are considered best practices by Microsoft. Exchange is site specific so it is going to look to your local site for its information by default and requires a global catalog so in your instance I would make all of your servers GC's and continue as Exchange will find server C acceptable. Of course prior to doing any Exchange work I would make all the DC's GC's then run dcdiag and repadmin to confirm that your AD replication and topology are working properly. Thanks, Jorge R. Diaz, PMP, CCNA, MCSA, MCSE Senior Microsoft Consultant Planet Technologies, Inc. Check out My Blog!

Exchange requires a DC and GC to operate. Preferrable in the same AD site. As far as what the columns in Event 2080 mean, check out: http://howdouc.blogspot.com/2011/01/exchange-active-directory-topology.html If your ultimate goal is to make Server C the primary server for Exchange request, then you need to make it a GC and fix some of the "zeros", see link above. Right now it would be unusable to Exchange. It should look like Server A or D. It is also recommended to have at least two usable servers in the same site for fault tolerance and to share the load.Tim Harrington | MVP: Exchange | MCITP: EMA 2007/2010, MCITP: Server 2008, MCTS: OCS | Blog: http://HowDoUC.blogspot.com | Twitter: @twharrington

Hello, Yesterdag evening I marked server C as GC. THis morning, about 12 hours later event ID 2080 hasnt changed its output. How long should this change take? Do I need to restart the service and by consequence Exchange? Thx for 2 very helpfull replies! Regards, Jelle

Update! Server C changed to CDG 1 0 0 1 0 0 0 0 0 So its being recognised as config server, DC and Global Catalog, nice! I guess I should wait a bit more for more 0's to turn into 1's. I'll keep you guys updated.

Yeah, it should be pretty quick. Not sure what you set your site-to-site replication to but the default is 120 minutes. You can always force replication as well by going into sites and services, right clicking the server links and select 'replicate now'. Sounds like you are on the right path, keep us posted on the progress. Jorge R. Diaz, PMP, CCNA, MCSA, MCSE Senior Microsoft Consultant Planet Technologies, Inc. Check out My Blog!

Hello, It's been 2 days now yet Server C still shows CDG 1 0 0 1 0 0 0 0 0 I updates the links as suggested. Plz advise. Ty. Regards, Jelle

I've found this error in Server C event log : The name "Donaminname :1d" could not be registered on the Interface with IP address ... Trying fixes descibed here : http://www.eventid.net/display.asp?eventid=4321&eventno=1822&source=NetBT&phase=1 - checked WINS - disabled LMHOST lookup - reboot server C No dice :(

Success! Server C is now showing exactly the same output as other GC's. CDG 1 7 7 1 0 1 1 7 1 Something mentioned here http://www.eventid.net/display.asp?eventid=4321&eventno=1822&source=NetBT&phase=1 or the fact a Linux machine was trying to propagate as preferred GC. I will make the Exchange change on monday, i'll post more results then. Great way to start the weekend this!! :)))

Talking to the walls over here, but maybe some day this can help someone.. =) I updated AD servers being used with cmdlet Set-ExcangeServer -identity "server" -StaticExcludedDomainControllers {"server A","server B"} -StaticDomainControllers {"server C","server CD"} I used the EMS to change the CurrentConfigDomainController All is reporting ok on 1 of our 4 exchange servers. Next monday i'll change the other servers and the week after that i'll start decommissioning server A and B. Thx for all you're help! Regards, Jelle